Tree preservation zone

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

1 Bemersyde Drive

reference: 1983/003.T1
name: 1 Bemersyde Drive
tree-preservation-order: undefined
1983/003.T1
tree-preservation-zone-type: individual
geometry: MULTIPOLYGON (((-1.604853 54.997835,-1.605010 54.997836,-1.605011 54.997746,-1.604854 54.997745,-1.604853 54.997835)))
point: POINT (-1.604932 54.997791)
notes: These data are update live via a feed to NCC's Tree Managament System, EzyTreev
entry-date: 1983-01-01
start-date: 1983-01-01
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

This diagram shows the relationship between the tree preservation order dataset and the tree preservation zone dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree preservation zone dataset.

How to improve Newcastle City Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL